Received: from heifetz.msen.com by merit.edu (5.65/1123-1.0)
id AA26516; Wed, 3 Jun 92 13:58:52 -0400
Received: by heifetz.msen.com (/\==/\ Smail3.1.22.1 #22.11)
id <m0lszat-000HeDC@heifetz.msen.com>; Wed, 3 Jun 92 13:57 EDT
Received: by one.one.com (/\==/\ Smail3.1.24.1 #24.5)
id <m0lszaX-00015rC@one.one.com>; Wed, 3 Jun 92 13:57 EDT
Received: by norton.one.com (/\==/\ Smail3.1.24.1 #24.15)
id <m0lszbY-00013BC@norton.one.com>; Wed, 3 Jun 92 13:58 EDT
Message-Id: <m0lszbY-00013BC@norton.one.com>
Date: Wed, 3 Jun 92 13:58 EDT
From: rrb@one.com (Russ Blaesing)
To: skh@merit.edu
Subject: TP MIB
If this is a duplicate message please disregard.
I have been developing a OSI Transport MIB for use in an encryption system.
Dave Piscitello told me I should send you the MIB and ask you whether you
felt it could be put in your NOOP group, or whether we should have a BOF
meeting at the IETF meeting in July.
Please let me know ASAP what your feeling are about this. I would like to
know what level of participation will be required from me to see this MIB
progress to an experimental status. What is the normal procedure for this
sort of MIB?
Thanks,
-Rb
-------------------------------------------------------------------------- Russell R. Blaesing (Russ) Open Networks Engineering, Inc. (ONE) Voice: (313) 996-9900 777 E. Eisenhower Parkway, Suite 315 Fax: (313) 996-9908 Ann Arbor, MI 48108 Internet: rrb@one.com --------------------------------------------------------------------------
================== TP MIB ================
INTERNET-DRAFT TP MIB MAY 1992
INTERNET-DRAFT Russell R. Blaesing
James A. Verploegh
Open Networks Engineering, Inc.
MAY 1992
ISO Transport Protocol (ISO 8072 & ISO 8073)
Management Information Base
Status of this Memo
This memo defines an experimental version of an ISO
Transport Management Information Base for use with
network management protocols in TCP/IP-based internets.
This memo does not specify a standard for the Internet
community. However, after experimentation, if
sufficient consensus is reached in the Internet
community, then a subsequent revision of this document
may be placed in the Internet-standard MIB. This draft
document will be submitted to the RFC editor as a
protocol specification. Distribution of this memo is
unlimited. Please send comments to Russell Blaesing:
rrb@one.com.
Distribution of this memo is unlimited.
Blaesing & Verploegh page 1
INTERNET-DRAFT TP MIB MAY 1992
Table of Contents
1. Abstract.................................2
2. Introduction.............................2
3. Objects..................................2
4. Object Definitions.......................3
5. Acknowledgements.........................15
6. References...............................15
7. Security Considerations..................17
8. Authors' Addresses.......................17
1. Abstract
This memo defines an experimental version of an ISO
Transport Management Information Base for use with
network management protocols.
2. Introduction
This document defines an ISO Transport Management
Information Base for use with the network management
protocols. The ISO Transport network management
document [10] was used as a basis for this document.
The ISO Transport network management document [10] is a
draft document out for comment. The comment period
ended May 22, 1991. Therefore, this INTERNET-DRAFT may
change to accomodate any changes reflected in the final
version of the ISO Transport network management
document [10].
3. Objects
The objects described in this document use the format
described in the "Concise MIB Definitions" document
[6]. This document should be referenced to fully
understand section 4.
Consistent with the IAB directive to produce simple,
workable systems in the short-term, the list of managed
objects defined here, has been derived by taking only
those elements which are considered essential. This
document only describes ISO Transport class 4 specific
objects.
Blaesing & Verploegh page 2
INTERNET-DRAFT TP MIB MAY 1992
4. Object Definitions
INTERNET-DRAFT-MIB DEFINITIONS ::= BEGIN
IMPORTS
experimental, Counter, Gauge
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212;
-- This MIB module uses the extended OBJECT-TYPE
-- macro as defined in SMI [2];
tp OBJECT IDENTIFIER ::= { experimental 1 }
-- The following objects correspond to objects within
-- the Transport Entity Managed Object as defined by
-- ISO/IEC CD 10737.
tpUndecodedNSDUs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of network layer service data
units (NSDUs) that were received that could
not be associated with a valid t-selector
(tsapID)."
::= { tp 1 }
tpChksumErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of Transport PDUs received with
incorrect checksum."
::= { tp 2 }
tpProtocolErrors OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of Transport PDUs received with
an invalid header."
::= { tp 3 }
Blaesing & Verploegh page 3
INTERNET-DRAFT TP MIB MAY 1992
-- The following objects correspond to objects within
-- the Connection-Oriented Transport protocol Machine
-- Managed Object as defined by ISO/IEC CD 10737.
tpSentOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of user data octets sent. Do not
include data in non-DT TPDUs, or DT TPDUs
that were rejected."
::= { tp 4 }
tpRcvdOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of user data octets received in
valid DT PDUs. Do not include data in non-
DT TPDUs, or DT TPDUs that were rejected."
::= { tp 5 }
tpOpenConns OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of transport connections
currently in the open state."
::= { tp 6 }
tpMaxConns OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum number of simultaneously open
transport connections allowed."
::= { tp 7 }
tpLocSuccessConns OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
Blaesing & Verploegh page 4
INTERNET-DRAFT TP MIB MAY 1992
"The number of locally initiated transport
connections that reached the open state."
::= { tp 8 }
tpRemSuccessConns OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of remotely initiated transport
connections that reached the open state."
::= { tp 9 }
tpLocUnsuccessfulConns OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of locally initiated transport
connections that did not reach the open
state. Pending connections are not
considered in this counter."
::= { tp 10 }
tpRemlyUnsuccessfulConns OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of remotely initiated transport
connections that did not reach the open
state."
::= { tp 11 }
tpLocDiscErrs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of transport disconnects
initiated by the local entity that do not
have a reason code of 128 (normal
disconnect)."
::= { tp 12 }
tpRemDiscErrs OBJECT-TYPE
SYNTAX Counter
Blaesing & Verploegh page 5
INTERNET-DRAFT TP MIB MAY 1992
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of transport disconnects
initiated by the peer entity that does not
have a reason code of 128 (normal
disconnect)."
::= { tp 13 }
tpUnassocTPDUs OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of transport PDUs that could not
be associated with a valid transport
reference number."
::= { tp 14 }
tpMaxOpenConns OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The highest number of transport connections
to simultaneously be in the open state.
This may only be set to the value 0 (reset),
which has the effect of setting the value to
the current value of tpOpenConns."
::= { tp 15 }
-- The following objects correspond to objects within
-- the Transport Conn Initial Value Managed
-- Object as defined by ISO/IEC CD 10737.
tpProtocolClasses OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The set of protocol classes that may be
stated at connection establishment. Each
class supported is represented as a bit with
class 0 being bit 1, class 1 begin bit 2,
etc. This may be represented in 'C' as:
tpClassesSupported = 1 << first_class |
1 << second_class"
Blaesing & Verploegh page 6
INTERNET-DRAFT TP MIB MAY 1992
::= { tp 16 }
tpClassesSupported OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The set of protocol classes that are
supported by the implementation. Each class
supported is represented as a bit with class
0 being bit 1, class 1 begin bit 2, etc.
This may be represented in 'C' as:
tpClassesSupported = 1 << first_class |
1 << second_class"
::= { tp 17 }
tpExtendedFormat OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Enables the negotiation of the extended TPDU
format. TRUE (1) enables use of extended
format, FALSE (2) disables it."
::= { tp 18 }
tpChksum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Enables negotiation of checksum non-use.
TRUE (1) enables non-use, FALSE (2) disables
it."
::= { tp 19 }
tpInitInactTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Value to use for the inactivity timer(I)."
::= { tp 20 }
tpInitRetransTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-write
Blaesing & Verploegh page 7
INTERNET-DRAFT TP MIB MAY 1992
STATUS mandatory
DESCRIPTION
"Value to use for the local retransmission
timer(T1). The value may change adaptively
during the lifetime of the connection, and
another value may be adopted initially based
on knowledge concerning the remote system.
The value of this object is used in the
absence of other information."
::= { tp 21 }
tpInitWindowTimer OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Value to use for the window timer(W).
Meaningful for Class 4 only."
::= { tp 22 }
tpMaxWindow OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum window to be given on a
connection at any time. Buffering or other
implementation constraints or policies may
cause a smaller value to be used."
::= { tp 23 }
tpMaxTPDUSize OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The maximum allowable TPDU size to
negotiate. Implementations constraints or
policies may cause a smaller value to be
used."
::= { tp 24 }
tpMaxRetrans OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
Blaesing & Verploegh page 8
INTERNET-DRAFT TP MIB MAY 1992
"The maximum number of retransmissions of a
TPDU."
::= { tp 25 }
tpExplicitFlowCtl OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Enables negotiation of explicit flow
control for Class 2. TRUE (1) enables
negotiation, FALSE (0) disables
negotiation."
::= { tp 26 }
tpAckTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The value of the Acknowledgement timer in
use by the transport."
::= { tp 27 }
-- The following objects correspond to objects within
-- the Transport Connection Managed Object as
-- defined by ISO/IEC CD 10737.
tpConnTable OBJECT-TYPE
SYNTAX SEQUENCE OF TpConnEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The table of connection information."
::= { tp 28 }
tpConnEntry OBJECT-TYPE
SYNTAX TpConnEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"The connection entry for a transport
connection"
INDEX { tpConnLocRef }
::= { tpConnTable 1 }
TpConnEntry ::=
Blaesing & Verploegh page 9
INTERNET-DRAFT TP MIB MAY 1992
SEQUENCE {
tpConnLocRef INTEGER,
tpConnState INTEGER,
tpConnUpTime INTEGER,
tpConnProtocolClass INTEGER,
tpConnExpedited INTEGER,
tpConnExtendedFormat INTEGER,
tpConnChksum INTEGER,
tpConnInactTime INTEGER,
tpConnRetransTime INTEGER,
tpConnWindowTimer INTEGER,
tpConnMaxTPDUSize INTEGER,
tpConnMaxTrans INTEGER,
tpConnRemRef INTEGER,
tpConnTSelCalling INTEGER,
tpConnTSelCalled INTEGER,
tpConnNSAPCalling OCTET STRING,
tpConnNSAPCalled OCTET STRING,
tpConnDirection INTEGER,
tpConnSentPdus Counter,
tpConnRcvdPdus Counter,
tpConnSentOctets Counter,
tpConnRcvdOctets Counter,
tpConnRetransPdus Counter,
tpConnDupPdus Counter,
tpConnRetransOctets Counter,
tpConnDupOctets Counter
}
tpConnLocRef OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The local connection reference number."
::= { tpConnEntry 1 }
tpConnState OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The state of the connection. Note that the
closed and ref-wait states are invalid,
since the connection entry will not
normally be saved. Values are: wfcc(0),
Blaesing & Verploegh page 10
INTERNET-DRAFT TP MIB MAY 1992
wbcl(1), open(2), wftreps(3), ackwait(4),
closing(5)."
::= { tpConnEntry 2 }
tpConnUpTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The amount of time the connection has
been in the OPEN state. Not valid for
states other than OPEN."
::= { tpConnEntry 3 }
tpConnProtocolClass OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The protocol class being used by the
transport connection. During connection
establishment (before the connection reaches
the OPEN state) this indicates what is
currently preferred and not necessarily the
ultimate Class that will be used for the
connection. Possible values are class0(0),
class1(1), class2(2), class3(3), and
class4(4)"
::= { tpConnEntry 4 }
tpConnExpedited OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether the transport expedited
services is provided on this connection.
Values are TRUE(1), FALSE(0)."
::= { tpConnEntry 5 }
tpConnExtendedFormat OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
Blaesing & Verploegh page 11
INTERNET-DRAFT TP MIB MAY 1992
"Indicates whether normal or extended format
is used. TRUE (1) indicates that extended
format is being used, FALSE (2) indicates
that normal format is being used. During
connection establishment, this attribute
represents the desired value and not
necessarily the value that will ultimately
be used."
::= { tpConnEntry 6 }
tpConnChksum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether checksum non-use has been
selectoed for the connection (TRUE (1)) or
not (FALSE (2)). During connection
establishment, this attribute represents
the desired value and not necessarily the
value that will ultimately be used."
::= { tpConnEntry 7 }
tpConnInactTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the inactivity timer(I) in use
for the connection."
::= { tpConnEntry 8 }
tpConnRetransTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The current value of the retransmission
timer(T1) in use for the connection. The
value may change during the lifetime of the
connection, based on observations of traffic
on the connection or other information
concerning the remote transport entity."
::= { tpConnEntry 9 }
tpConnWindowTimer OBJECT-TYPE
SYNTAX TimeTicks
Blaesing & Verploegh page 12
INTERNET-DRAFT TP MIB MAY 1992
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the window timer(W) in use for
the connection."
::= { tpConnEntry 10 }
tpConnMaxTPDUSize OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the maximum TPDU size
negotiated for the connection. During
connection establishment, this attribute
represents the desired value and not
necessarily the value which will ultimately
be used."
::= { tpConnEntry 11 }
tpConnMaxTrans OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The value of the maximum number of
transmissions(N) used by the transport
connection."
::= { tpConnEntry 12 }
tpConnRemRef OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The remote conection reference number."
::= { tpConnEntry 13 }
tpConnTSelCalling OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The calling TSAP-ID specified during
connection establishment."
::= { tpConnEntry 14 }
Blaesing & Verploegh page 13
INTERNET-DRAFT TP MIB MAY 1992
tpConnTSelCalled OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The called TSAP-ID specified during
connection establishment."
::= { tpConnEntry 15 }
tpConnNSAPCalling OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The calling NSAP address specified at the
network service interface conveyed in the
Transport CR PDU."
::= { tpConnEntry 16 }
tpConnNSAPCalled OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The called NSAP address specified at the
network service interface conveyed in the
Transport CR PDU."
::= { tpConnEntry 17 }
tpConnDirection OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates the direction of the connection.
The value Incoming (1) means that it was
initiated by the remote transport entity,
the value outgoing (0) means that it was
initiated by the local transport entity."
::= { tpConnEntry 18 }
tpConnSentPdus OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
Blaesing & Verploegh page 14
INTERNET-DRAFT TP MIB MAY 1992
"The total number of TPDUs transmitted
(excluding retransmissions)."
::= { tpConnEntry 19 }
tpConnRcvdPdus OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of TPDUs received
associated to the transport connection
(excluding duplicates)."
::= { tpConnEntry 20 }
tpConnSentOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of user data octets sent on
the transport connection (excluding
retransmissions)."
::= { tpConnEntry 21 }
tpConnRcvdOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of user data octets
received on the transport connection
(excluding duplicates)."
::= { tpConnEntry 22 }
-- The following objects are not in the ISO Transport
-- Layer Management Specification. However, they are
-- seen as important objects to determine the
-- performance characteristics of the transport
-- layer. These values would be instrumentatal in
-- determining the proper value for the
-- retransmission timers.
tpConnRetransPdus OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
Blaesing & Verploegh page 15
INTERNET-DRAFT TP MIB MAY 1992
"The total number of TPDUs retransmitted."
::= { tpConnEntry 23 }
tpConnDupPdus OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of duplicate TPDUs received
associated to the transport connection."
::= { tpConnEntry 24 }
tpConnRetransOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of user data octets re-
transmitted on the transport connection."
::= { tpConnEntry 25 }
tpConnDupOctets OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The total number of duplicate user data
octets received on the transport
connection."
::= { tpConnEntry 26 }
END
5. Acknowledgements
James Reinstedler (Member of SNMP Working Group)
Ungermann Bass, Inc
3990 Freedom Circle
Santa Clara, California 95050
Sri Dikar Raman
The Wollongong Group, Inc.
1129 San Antonio Road
P.O. Box 51860
Palo Alto, California 94303
Blaesing & Verploegh page 16
INTERNET-DRAFT TP MIB MAY 1992
6. References
[1] Cerf, V., "IAB Recommendations for the Development
of
Internet Network Management Standards", RFC 1052, NRI,
April 1988.
[2] Rose M., and K. McCloghrie, "Structure and
Identification of
Management Information for TCP/IP-based internets", RFC
1155,
Performance Systems International, Hughes LAN Systems,
May 1990.
[3] McCloghrie, K. and Rose, M.T., "Management
Information
Base for network management of TCP/IP-based internets",
RFC 1156,
Performance Systems International, Hughes LAN Systems,